Harden review workflows and deliver comments in FIFO order - #8

What this changes

This PR contains every change currently on fix/code-scanning-findings and not on main. It ships Visual Stack 6.7.0 across the Claude and Codex manifests.

• Hardens review and experimental pages against attribute injection, prototype mutation, forged output lines, unsafe temporary cache ownership, and malformed closing-tag handling. It also centralizes literal changelog-section parsing for release scripts.
• Gives Codex durable bounded-pull review delivery with explicit offer/claim semantics and a renewable consumer lease. Claude and Grok retain push delivery behind the same host contract.
• Serializes review work across all hosts: one active comment at a time, FIFO. New comments cannot interrupt active work; asking a question releases the slot, and a reviewer answer rejoins the queue at reply time.
• Keeps a pull Host's review loop from stopping silently. A bounded wait continues only while the agent keeps calling it, and every exit from that loop said nothing about calling again: IDLE returned after 25 seconds, and a claim reported its round, while nothing was left running to notice the calls had stopped. Comments then sat undelivered behind an expired lease. Each exit now prints the quoted command that resumes the wait, as the one-shot push form already did.
• Stops unanswered reporting all-clear over a review nobody is watching. With nothing ever delivered it confirmed that every comment was closed or answered, which is the check an agent runs before ending a turn. It now names a live review with comments waiting and no watcher behind it, stays quiet while a pull lease is fresh, and leaves its exit code alone — only a round this session was handed and left unanswered blocks a turn, per rule 14.
• Updates the workspace states, recovery behavior, contracts, host profiles, skill instructions, lifecycle diagram, changelog, and E2E coverage for those semantics. The README now says plainly that Codex support is experimental and why.
• Stabilizes browser E2E scrolling by waiting for the review frame to be laid out before scrolling, restores the working Security and Scorecard badges, and ignores local plugin-install bookkeeping.

How it was tested

• node plugins/vstack/skills/review/tests/review-lifecycle.mjs, now run from a directory whose name contains a space, which is what caught the argument quoting in the resume commands
• node plugins/vstack/skills/review/tests/round-gate.mjs
• Host-profile, workdir, update-check, and design-token test suites
• Full default Cucumber profile: 37 scenarios / 276 steps, under both VSTACK_HOST=claude and VSTACK_HOST=codex
• Browser profile: 16 scenarios / 124 steps
• Strict validation of both plugin manifests
• Stamped-shell check, JavaScript syntax check, and git diff --check
• The delivery-loop failure was reproduced first against a real review server — six comments queued, server up — and the same reproduction was re-run against the installed copy on both hosts to confirm the fix in the code each host actually loads
• All 14 GitHub CI and security checks pass on the final commit

Checklist

• Installed the plugin from this branch on both hosts and drove the review delivery loop end to end against the installed copy: publish, serve, bounded wait, claim, publish, unanswered. Automated host E2E covers the rest.
• No new unstated external write or transmission was introduced.
• Pages remain self-contained with no external runtime requests.
• The shared shell was stamped and verified current.
• Both host manifests are versioned 6.7.0 with matching 6.5.0, 6.6.0 and 6.7.0 changelog entries.
• Final GitHub CI and security scans pass. No code-scanning alerts remain open on this branch; alerts 24, 62 and 63 are open on main and resolved here.

Not applicable: no plugin or tool was added or renamed, and no workflow action was added.